home *** CD-ROM | disk | FTP | other *** search
- Path: news.iadfw.net!usenet
- From: Larry Weiss <lfw@iadfw.net>
- Newsgroups: comp.lang.c
- Subject: Re: #include --> Question
- Date: Thu, 29 Feb 1996 06:20:21 -0600
- Organization: ...
- Message-ID: <31359A05.4014@iadfw.net>
- References: <4gvp2c$sdr$1@mhafc.production.compuserve.com> <4h1d2l$4n3@pyrrhus-f.hrz.tu-chemnitz.de> <4h2si8$1bf@solutions.solon.com>
- NNTP-Posting-Host: dal02-13.ppp.iadfw.net
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0 (Win16; I)
-
- Peter Seebach wrote:
- >
- > The character '\' introduces undefined behavior in a header file name.
- >
-
- Peter, are you sure about this? Can you cite a clause of the Standard?
-
- I'm looking at Clause 6.8.2 and 6.1.7. The only characters that cannot be
- used in a #include "name" header name according to those sections are
- newline and doublequote.
-
- Of course, all interpretation of the characters used to signify a
- #include "name" are implementation defined.
-